System for processing insurance coverage requests

ABSTRACT

A system for processing insurance coverage requests. An insurance data processing system (IDPS) implements a method that processes the requests. The IDPS receives at least one request from a customer relating to insurance coverage for the customer. Each request independently requests activation or deactivation of the insurance coverage. The requests are ordered in a time sequence if the at least one request includes more than one request. The IDPS verifies, for each request received, that it is permissible for the IDPS to accommodate each request. After each request is verified, the IDPS archives each request in a non-volatile storage medium of the IDPS.

This application is a continuation application claiming priority to Ser.No. 12/336,001, filed Dec. 16, 2008, now U.S. Pat. No. 7,774,218, issuedAug. 10, 2010; which is a continuation application of Ser. No.11/505,162, filed Aug. 15, 2006 which is now U.S. Pat. No. 7,469,215,issued Dec. 23, 2008.

FIELD OF THE INVENTION

The present invention relates to a method and system for processinginsurance coverage requests.

BACKGROUND OF THE INVENTION

Numerous insurance products are available for insuring life and health,and for insuring many different types of property including vehicles,homes, and business. Some of these insurables may require fulltimeinsurance coverage on a year-round basis. However, for other types ofassets, fulltime coverage may not be necessary.

For example, for automobiles, insurance coverage is often obtained for afixed term, and renewed periodically thereafter. This is generally areasonable arrangement for a primary transportation vehicle that isoperated regularly. However, certain types of vehicles may be operatedonly on a seasonal basis, or only occasionally or intermittently. Forvehicles that are operated seasonally, it may still be possible toobtain insurance coverage in a conventional manner, based onpredetermined start and stop dates. However, this approach may limitflexibility.

What is needed is a more flexible system and method for providinginsurance coverage.

SUMMARY OF THE INVENTION

The present invention provides a method for processing insurancecoverage requests, said method comprising:

receiving, by an insurance data processing system (IDPS), at least onerequest from a customer relating to insurance coverage for the customer,each request independently requesting activation or deactivation of theinsurance coverage, the requests of the at least one request beingordered in a time sequence if the at least one request comprises morethan one request;

verifying by the IDPS, for each request received, that it is permissiblefor the IDPS to accommodate each request; and

after said verifying for each request, archiving by the IDPS eachrequest in a non-volatile storage medium of the IDPS.

The present invention provides an insurance data processing system(IDPS) for processing insurance coverage requests, said systemcomprising:

means for receiving a request from a customer relating to insurancecoverage for the customer, said request requesting activation ordeactivation of the insurance coverage;

means for verifying that it is permissible for the IDPS to accommodatethe request; and

means for archiving the request in a non-volatile storage medium of theIDPS after the request is verified.

The present invention provides a data processor readable medium storingdata processor code that, when loaded into a data processing device,adapts the device to perform method of processing insurance coveragerequests, said method comprising:

receiving, by an insurance data processing system (IDPS), at least onerequest from a customer relating to insurance coverage for the customer,each request independently requesting activation or deactivation of theinsurance coverage, the requests of the at least one request beingordered in a time sequence if the at least one request comprises morethan one request;

verifying by the IDPS, for each request received, that it is permissiblefor the IDPS to accommodate each request; and

after said verifying for each request, archiving by the IDPS eachrequest in a non-volatile storage medium of the IDPS.

The present invention provides a more flexible system and method forproviding insurance coverage than exists in the related art.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a generic data processing system that may provide asuitable operating environment, in accordance with embodiments of thepresent invention.

FIG. 2 shows an illustrative schematic diagram of an insurance dataprocessing system (IDPS) for activating insurance coverage on demand, inaccordance with embodiments of the present invention.

FIG. 3A and FIG. 3B show an illustrative example of a mobile electronicdevice for use in the system of FIG. 2, in accordance with embodimentsof the present invention.

FIG. 4 shows a flowchart of an illustrative insurance activation method,in accordance with embodiments of the present invention

FIG. 5 shows a flowchart of an illustrative method of utilizing thedevice of FIG. 3A and FIG. 3B to activate insurance coverage, inaccordance with embodiments of the present invention.

FIG. 6 shows a flowchart of an illustrative method for verifyingactivation of insurance coverage, in accordance with embodiments of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention relates to a system and method for activatinginsurance coverage, and for facilitating subsequent verification ofinsurance activation for the purposes of processing an insurance claim.

In an aspect of the invention, there is provided a system for activatinginsurance coverage, comprising: activation means operable by a customerfor activating insurance coverage; verification means for verifyingwhether activation of insurance coverage is permissible; a timer forproviding the date and time of activation of insurance coverage by thecustomer; non-volatile storage means for archiving instances ofactivation of insurance coverage by the customer, together with the dateand time of activation.

In an embodiment, the timer is synchronized to a standard broadcast timesignal.

In another embodiment, the activation means includes authorization meansfor authorizing the customer to request the activation of insurancecoverage.

In yet another embodiment, the system further comprises a deactivationmeans operable by the customer for deactivating insurance coverage.

In another embodiment, the date and time of activation of insurancecoverage predetermines deactivation of insurance coverage after a setperiod of time.

In a further embodiment, the non-volatile storage means is one oftamper-proof and tamper-evident, and auditable for verification ofactivation of insurance coverage in the event of an insurance claim.

In another embodiment, the activation means operated by the customer issynchronized to one of the timer and the standard broadcast time signal.

In still another embodiment, the activation means comprises a mobileelectronic device operable in an offline mode, the mobile electronicdevice having an internal clock synchronized to one of the timer and astandard broadcast time signal, and an internal non-volatile storagemeans for archiving instances of insurance coverage activation by thecustomer together with the date and time of activation while operatingin the offline mode.

In another embodiment, the internal non-volatile storage means is one oftamper-proof and tamper-evident, and auditable for verification ofactivation of insurance coverage in the event of an insurance claim.

In another aspect of the invention, there is provided a method ofactivating insurance coverage, comprising: providing an activation meansoperable by a customer for activating insurance coverage; verifyingwhether activation of insurance coverage is permissible; obtaining froma timer the date and time of activation of insurance coverage by thecustomer; archiving in a non-volatile storage means instances ofactivation of insurance coverage by the customer, together with the dateand time of activation.

In an embodiment, the method further comprises synchronizing the timerto a standard broadcast time signal.

In another embodiment, the method further comprises providingauthorization means for authorizing the customer to request theactivation of insurance coverage.

In still another embodiment, the method further comprises providing adeactivation means operable by the customer for deactivating insurancecoverage.

In another embodiment, the method further comprises predeterminingdeactivation of insurance coverage in dependence upon the date and timeof activation of insurance coverage.

In a further embodiment, the non-volatile storage means is one oftamper-proof and tamper-evident, and the method further comprisesauditing the non-volatile storage means for verification of activationof insurance coverage in the event of an insurance claim.

In another embodiment, the method further comprises synchronizing theactivation means operated by the customer to one of the timer and thestandard broadcast time signal.

In yet another embodiment, the method further comprising providing amobile electronic device operable in an offline mode, the mobileelectronic device having an internal clock synchronized to one of thetimer and a standard broadcast time signal, and an internal non-volatilestorage means for archiving instances of insurance coverage activationby the customer together with the date and time of activation whileoperating in the offline mode.

In still another embodiment, the internal non-volatile storage means isone of tamper-proof and tamper-evident, and the method further comprisesauditing the internal non-volatile storage means for verification ofactivation of insurance coverage in the event of an insurance claim.

In another aspect of the invention, there is provided a data processorreadable medium storing data processor code that, when loaded into adata processing device, adapts the device to activate a customer'sinsurance coverage, the data processor readable medium including: codefor verifying whether activation of insurance coverage requested by thecustomer is permissible; code for obtaining from a timer the date andtime of activation of insurance coverage by the customer; code forarchiving in a non-volatile storage means instances activation ofinsurance coverage by the customer, together with the date and time ofactivation.

In an embodiment, the data processor readable medium further includescode for synchronizing the timer to a standard broadcast time signal.

In another embodiment, the data processor readable medium furtherincludes code for authorizing the customer to request the activation ofinsurance coverage.

In yet another embodiment, the data processor readable medium furtherincludes code for providing a deactivation means operable by thecustomer for deactivating insurance coverage.

In still another embodiment, the data processor readable medium furtherincludes code for predetermining deactivation of insurance coverage independence upon the date and time of activation of insurance coverage.

In another embodiment, the data processor readable medium furtherincludes code for auditing the non-volatile storage means forverification of activation of insurance coverage in the event of aninsurance claim.

In a further embodiment, the data processor readable medium furtherincludes code for synchronizing the activation means operated by thecustomer to one of the timer and the standard broadcast time signal.

As noted above, the present invention relates to a method and system foractivating insurance coverage, and for facilitating subsequentverification of activation of insurance coverage for processing aninsurance claim.

As will be explained infra, the invention may be embodied in variousphysical configurations which may include data processing systems,networks, devices, software and firmware. The particular configurationsshown by way of example in this specification are not meant to belimiting.

FIG. 1 shows a generic data processing system 100 that may include acentral processing unit (“CPU”) 102 connected to a storage unit 104 andto a random access memory 106, in accordance with embodiments of thepresent invention. The CPU 102 may process an operating system 101,application program 103, and data 123. The operating system 101,application program 103, and data 123 may be stored in storage unit 104and loaded into memory 106, as may be required. An operator 107 mayinteract with the data processing system 100 using a video display 108connected by a video interface 105, and various input/output devicessuch as a keyboard 110, mouse 112, and disk drive 114 connected by anI/O interface 109. In known manner, the mouse 112 may be configured tocontrol movement of a cursor in the video display 108, and to operatevarious graphical user interface (“GUI”) controls appearing in the videodisplay 108 with a mouse button. The disk drive 114 may be configured toaccept data processing system readable media 116. The data processingsystem 100 may form part of a network via a network interface 111,allowing the data processing system 100 to communicate with othersuitably configured data processing systems (not shown).

FIG. 2 shows an illustrative schematic diagram of an insurance dataprocessing system (IDPS) 200 for activating and deactivating insurance“on demand”, in accordance with embodiments of the present invention.System 200 may contain one or more data processing systems, such as thedata processing system 100 illustrated in FIG. 1, in standalone ornetworked configurations.

The system 200 shown in FIG. 2 comprises: an insurance activation server202; an archive database 208 connected to the insurance activationserver 202; a status change database 210 connected to the insuranceactivation server 202; an insurance database 214 connected to theinsurance activation server 202; a claim processing server 216 connectedto the insurance activation server 202; a date/time server 212 connectedto the insurance activation server 202, the insurance database 214, theclaim processing 216; and mobile electronic device 300.

As shown in FIG. 2, an insurance activation server 202 may interact withone or more access devices 204, 206, 300 operated by one of customers201 a, 201 b and 201 c (collectively customer 201). Insurance activationserver 202 may be, for example, a generic data processing system (e.g.data processing system 100) appropriately configured as a server. Asshown by way of example, the access devices may include a telephone 204,a computer 206, and a mobile electronic device 300. (An illustrativeexample of a mobile electronic device 300 is described with reference toFIGS. 3A and 3B below.)

Insurance activation server 202 may be operatively connected to a securearchive database 208 for logging or archiving each instance of aninstruction for activation of insurance coverage received from customer201. Insurance activation server 202 may also be operatively connectedto a status change database 210 for updating and maintaining a currentstatus for insurance coverage for a particular customer 201. Archivedatabase 208 and status change database 210 may reside either ondifferent physical storage devices, or on the same physical storagedevice provided that appropriate access controls and restrictions areput in place for each database.

Date/time server 212 may be used to synchronize the date and time fortracking activation of insurance coverage within system 200. Date/timeserver 212 may be synchronized to a standard broadcast date and timesignal that may also be used by telephone 204, computer 206, and mobileelectronic device 300.

Insurance database 214 may store particular details and selectableinsurance coverage options for each insurance policy previously set upfor each customer 201 and entered into system 200. Insurance database214 may be configured to be accessible by insurance activation server202 for verification of the insurance policy and selectable options fora particular customer 201. Insurance database 214 may also be configuredto be accessible by claim processing 216 when subsequently processing aninsurance claim, as described further below.

As illustrated in FIG. 2, customer 201 may access insurance activationserver 202 using any one of a number of different activation means. Forexample, customer 201 may use a touchtone telephone 204 to accessinsurance activation server 202 via a suitable voice response unit orVRU 204 a interface. Telephone 204 may be a conventional landlinetelephone, a cell phone, a satellite phone, etc. that may be used toaccess VRU 204 a.

Telephone 204 may also be a miniature computer platform based cell phonewith random access memory and advanced data processing capabilities,allowing telephone 204 to store and execute mini-applications or“applets”. These applets may perform specific functions that wouldotherwise be performed using a suitably configured computer 206 (e.g.data processing system 100 of FIG. 1). A compatible computer modem ornetwork interface 206 a may provide customer 201 with access toinsurance activation server 202 and its various functions.

Customer 201 may also use a mobile electronic device 300, with asuitable communications interface 300 a that may be used to receivecommunications from device 300, and to send communications back todevice 300.

Whether customer 201 interacts with insurance activation server 202using a telephone 204, computer 206, mobile electronic device 300, orsome other access device, insurance activation server 202 may beaccessed to facilitate activation of insurance coverage on demand, aswill be described further below.

Insurance activation server 202 may be configured to provide high systemavailability in order for customers 201 to access insurance activationserver 202 at virtually any time, and to activate insurance coverage ondemand. However, in the event that immediate access to insuranceactivation server 202 is unavailable for whatever reason, customer 201may be given an option to activate insurance coverage “offline”. Thismay be achieved, for example, by using a suitably configured device thatis operable in an offline mode.

FIG. 3A and FIG. 3B show a device 300 that may be used in an offlinemode in system 200 of FIG. 2, in accordance with embodiments of thepresent invention. Device 300 may be issued, for example, by an insurerproviding customer 201 with insurance coverage that may be activated ondemand using device 300. Alternatively, an insurance broker or agent mayprovide the device 300 to consumers and act as an intermediary byproviding insurance coverage on demand from various insurers offeringcompeting insurance products.

As shown in FIG. 3A, illustrative device 300, comprised by the system200, includes a keypad 302 for inputting data, a display 304 forallowing customer 201 to view data, and data navigation keys 303 forscrolling through and selecting various options from a menu presented indisplay 304.

As shown schematically in FIG. 3B, illustrative device 300 may includevarious internal components. Device 300 and its internal componentsshould operate reliably, and be able to maintain date/time accuracy overa range of operating conditions.

Preferably, device 300 includes a mobile power source, such as a battery305. Device 300 may also include an auxiliary power source 307 (e.g.solar power cell), such that device 300 may be conveniently carried bycustomer 201 and kept operational over an extended period of time.Device 300 may also include a battery charger 306 for periodicallyrecharging battery 305, and an I/O interface 308 that may provide accessto a suitable communications/power connection port of a computer (e.g.to a Universal Serial Bus or USB port) via suitable protection circuitry310.

As shown, a power bus 312 connected to battery 305 and auxiliary powersource 307 may provide electrical power to a display unit 304, areal-time clock 316, a Micro-Controller Unit or MCU 318, an optionaltransmitter/receiver 330, and any other internal component requiringpower.

Still referring to FIG. 3A and FIG. 3B, display unit 304 may be a LiquidCrystal Display (LCD) or the like, and be controlled by MCU 318 toprovide customer 201 with feedback on data the customer 201 has enteredinto device 300 via key-pad 302. Display unit 304 may also displayvarious menu choices for navigation and selection of options by customer201.

Real-time clock 316 may be configured to keep track of date and time fordevice 300. Real-time clock 316 may be initially set by the issuer ofdevice 300, or otherwise be configured to automatically synchronize orresynchronize to a standard broadcast time signal so that device 300 issubstantially in synch with the date/time kept by date/time server 212of FIG. 2. Synchronization or resynchronization of the date and time mayoccur, for example, by receiving a standard broadcast time signal viatransmitter/receiver 330, or alternatively by receiving date/time datathrough I/O interface 308 when device 300 is connected to an externaldevice capable of providing date/time data.

Real-time clock 316 should preferably be tamper-proof, as it may be usedto audit the date and time of activation of insurance coverage bycustomer 201. Therefore, the synchronization or resynchronizationfunction as described above should not allow customer 201 to set thedate and time manually to something other than the actual date and time.As well, in order to maintain integrity and confidentiality of customerdata, any data transmitted between device 300 and insurance activationserver 202 or another external device should preferably be digitallyencrypted, and may be signed to identify an authorized access device, orotherwise secured.

Still referring to FIG. 3A and FIG. 3B, MCU 318 may be configured to runsuitable data processor readable code to control various functions ofdevice 300. For example, suitable data processor readable code mayactivate buzzer 320 to alert customer 201 to various warnings or errorconditions, such as low battery charge, etc.

MCU 318 may also be operatively connected via a data bus 322 to anon-volatile storage device 324, and to a read-only memory or ROM 326.ROM 326 may be configured to contain an Electronic Serial Number or ESNwhich uniquely identifies device 300. At the time of issue of device300, this ESN may be associated with a particular customer 201 touniquely identify the customer 201. ROM 326 may also contain operationalcode for MCU 318.

Non-volatile storage device 324 and ROM 326 should preferably betamper-proof or tamper-evident, such that integrity of data stored innon-volatile storage device 324 and ROM 326 can be assured for auditingpurposes in the event of a subsequent insurance claim made by customer201. By way of example, non-volatile storage device 324 may beconfigured as a Write-Once-Read-Many (WORM) type of storage withcapacity to record all instances of activation of insurance coverage bycustomer 201. Non-volatile storage device 324 may also be configured,for example, as a Programmable Read-Only Memory (PROM), which may bewritten to just once.

While the discussion above refers generally to activation of insurancecoverage by customer 201, it will be appreciated that system 200 and theaccess devices 204, 206, 300, may be configured such that customer 201may also deactivate insurance coverage on demand. However, to minimizethe risk of unintended changes, confirmation of an instruction foractivation or deactivation of insurance coverage preferably should besought prior to effecting the requested change.

By way of example, if an insurance deactivation option is enabled,device 300 may be configured with a single push button that can be usedby customer 201 to toggle between an activated or deactivated insurancecoverage state. Alternatively, a dual button design may be used, wherebyone button is used to activate insurance coverage, and the other is usedto deactivate insurance coverage.

In an embodiment, device 300 may be configured such that, when device300 is power up for the first time, device 300 operates continuouslyuntil customer 201 has a need to make an insurance claim, based on aninstance of insurance activation recorded in device 300. With a suitablepower source, continuous operation of device 300 may extend, forexample, for a year or more. In a subsequent reset of device 300 thatmay be necessitated by an exhausted power source or a reset condition(e.g. indicating a need to make an insurance claim), device 300 may beconfigured to awake in a locked read only mode, such that auditing andverification of insurance coverage can take place without any furtherchange in data or status being possible in device 300.

The operation of illustrative device 300 and its use within system 200of FIG. 2 will now be described in more detail.

FIG. 4 shows a flowchart of an illustrative method 400 for activating(or deactivating) insurance coverage, in accordance with embodiments ofthe present invention. At block 402 of method 400, a customer (e.g.customer 201) requests access (e.g. to an insurance activation server202) via a user interface device (e.g. via a telephone 204, a computer206, or a mobile electronic device 300), to activate or deactivateinsurance coverage for the customer 201.

Upon receiving the access request at block 402, method 400 proceeds todecision block 404, where customer 201 is required to identifyhimself/herself to ensure that the activation or deactivation ofinsurance coverage for customer 201 is effected only by an authorizedperson or persons. This authorization step may require customer 201 toidentify himself/herself by providing a userid or some other uniqueidentifier, and to enter a password or Personal Identification Number(PIN) associated with that userid or unique identifier. In theillustrative example of system 200, if customer 201 uses telephone 204to access a VRU 204 a, VRU 204 a may prompt customer 201 to enter anumeric userid or unique identifier using a key-pad on telephone 204.This may be followed by prompting customer 201 to enter a password orPIN associated with that userid or identifier. If a computer 206 isused, a password prompt may appear within a GUI window so that customer201 can input both a userid and password via a keyboard. If device 300is used, key-pad 302 may be used to enter a userid and to subsequentlyenter a PIN associated with that userid. Alternatively, the ESN for thedevice 300 may be used to uniquely identify the customer, and thereforeit may be necessary for the customer to enter only the PIN.

If customer 201 is not properly authorized at block 404, method 400 mayreturn to decision block 402. Once customer 201 has been authorized atdecision block 402, method 400 may proceed to block 406, where method400 may either proceed to block 408, or allow the connection to end(i.e., without making a change).

At block 408, customer 201 may be provided with menu options to allowcustomer 201 to select various insurance coverage options or to changestatus. In the illustrative example of system 200, if a telephone 204 isused, VRU 204 a may interact with insurance activation server 202 tooffer customer 201 a choice of options by recorded voice prompts.Customer 201 may then navigate and select an option by responding to VRU204 a voice prompts by inputting data via touchtone buttons on telephone204. If a computer 206 is used instead, a GUI interface may provide amenu from which customer 201 may select activation or deactivation ofinsurance coverage using a mouse or keyboard. If a mobile electronicdevice 300 is used, e.g. as illustrated in FIG. 3A and FIG. 3B, device300 may include a key-pad 302 and navigation keys 303 to allow customer201 to navigate and select menu options for activating or deactivatinginsurance coverage.

From block 408, method 400 proceeds to decision block 410 where thecoverage option or status change selected by customer 201 may beverified as being permissible (e.g. as verified against insurancedatabase 214 in system 200 of FIG. 2). The selection of the coverageoption or status change may comprise a request to the system 200 toactivate or deactivate insurance coverage for the customer 201. If theselected option or change in status is not verified as being permissibleat block 410, method 400 proceeds to block 414 to indicate that therequested status or option change is not valid. If the selected optionor change in status is validated at block 410, method 400 proceeds todecision block 412.

At decision block 412, method 400 may seek confirmation that customer201 wishes to change the status or options for insurance coverage. Thisconfirmation step is intended to minimize the possibility that acustomer 201 may unintentionally activate or deactivate insurancecoverage. If the selected change is not confirmed by customer 201 atblock 412, method 400 returns to block 414. If, on the other hand, thechange is confirmed by customer 201 at block 412, method 400 proceeds toblock 416, where the change in status or options is recorded and loggedin an archive database at 418 (e.g. in archive database 208 of FIG. 2).Preferably, any instance of activation or deactivation of insurancecoverage or selected options at block 412 should be permanently archivedat 418. The archive may then be later used to confirm the customer'sinstructions for activating or deactivating insurance coverage whenprocessing an insurance claim, as described further below.

From block 416, method 400 may then proceed to block 420 where theconfirmed status change can be stored at 422 in a status change database(e.g. status change database 210 of FIG. 2). Method 400 may then end.

FIG. 5 shows a flowchart of an illustrative method 500 of utilizing thedevice of FIG. 3A and FIG. 3B to activate insurance coverage withinsystem 200, in accordance with embodiments of the present invention.Method 500 begins at block 502 where, if device 300 is a not new device,method 500 proceeds to block 506 where all data write functions fordevice 300 may be disabled. This may correspond to waking up in a lockedread only mode in any “reset” of device 300, as previously mentioned.

Method 500 then proceeds to decision block 508 where method 500determines whether device 300 is connected to an external device orreader, such as computer, via its I/O interface 308. If yes, method 500may proceed to block 510 where data stored in non-volatile storage means324 (e.g. a PROM 324) is dumped to the external device or reader forprocessing. Otherwise, if device 300 is a new device, method 500proceeds to block 512, where device 300 is initialized, and PROM 324 maybe set to disable any further resets of device 300, e.g. when turned offand turned back on. Method 500 may then proceed to block 514, where dataassociated with customer 201 may be burned into PROM 324, and real-timeclock 316 is synchronized to a standard broadcast time signal (e.g. asprovided by a date/time server 212 of FIG. 2).

From block 514, method 500 proceeds to block 516, where method 500displays (e.g. via display 304) the current insurance status. If device300 is a new device that was just initialized, the initial defaultinsurance status may be non-active.

From block 516, method 500 proceeds to decision block 518, where method500 determines if customer 201 has requested activation of insurance. Aspreviously noted, in an embodiment, customer 201 may request activationof insurance by pressing an activation button on device 300.Alternatively, a menu selection for activating insurance coverage may beselected by customer 201 via display unit 314 and navigation keys 303.

If a change in activation status has been requested by customer 201,method 500 may proceed to decision block 520, where method 500determines whether device 300 presently has an available connection toinsurance activation server 202. If a connection is available, method500 may proceed to block 522 and communicate with system 200 in asubstantially analogous manner as described earlier with reference tomethod 400 of FIG. 4, for example.

If a connection is not available, method 500 may proceed to block 524,where device 300 performs its own authorization step by promptingcustomer 201 to enter a PIN, and then comparing the entered value with apreviously stored value (e.g. as stored in ROM 326 or in non-volatilestorage means or PROM 324). If the entered PIN is incorrect, an errormessage may be displayed at block 526 and method 500 may return to block536, described below. Otherwise, if the entered PIN is correct, method500 may proceed to block 528 where method 500 may read the currentstatus of insurance activation (e.g. as last stored in non-volatilestorage means 324).

From block 528, method 500 may proceed to decision block 530, anddetermine if the requested change in status is permitted by the currentstate of insurance activation. If yes, method 500 may proceed to block534 to update the status and write the request for change intonon-volatile storage means 324, together with the date and time, as readfrom real-time clock 316. Method 500 may then proceed to block 536,described below. If no, method 500 may proceed to display an errormessage at block 532, and proceed to decision block 536. If, at decisionblock 536, the PROM is not full, then method 500 may return to block516. Otherwise, method 500 may proceed to block 506 and disable furtherdata writes.

The customer 201 may issue requests (as described supra) in a timesequence such that each request independently requests activation ordeactivation of insurance coverage for the customer 201. For example,the customer 201 may issue the requests in a time sequence to togglebetween an insurance activated state and an insurance deactivated state.However, in an alternative embodiment, each request comprising instanceof activation of insurance coverage may start coverage for apredetermined amount of time, with no need for manual deactivation. Forexample, requesting insurance activation, and then confirming therequest for activation may activate insurance coverage for a fixed 24hour period before the insurance automatically expires. In thisalternative embodiment, customer 201 need only be concerned withactivating insurance coverage, for example, at the start of each day forwhich insurance coverage is desired.

In yet another embodiment, a block of time credits for insurancecoverage time may be purchased, such that customer 201 can activate anddeactivate insurance coverage on demand for as long as insurancecoverage time credits remains in a “bank” tracked by device 300. Use ofsuch credits may allow an insurer to provide different pricing pointsfor a given bundle of insurance credits, for example. Thus, for anindividual request requesting activation of the insurance coverage for atime duration, wherein insurance coverage time credit for insurancecoverage time has been previously purchased by the customer and includesa remaining amount of insurance time credit when the individual requestis received from the customer 201 by the system 200, the individualrequest may be verified to be permitted in step 410 of FIG. 4 or in step530 of FIG. 5 if the time duration does not exceed the remaining amountof insurance time credit.

If device 300 has been operated in offline mode, once a connection toinsurance activation server 202 has been re-established, an update ofarchive database 208 and status change database 210, with the datapreviously stored into non-volatile storage means 324 in step 534, mayoccur (e.g., may automatically occur), such that device 300 and the restof system 200 are once again synchronized. Thus, data stored innon-volatile storage means 324 may be copied and recorded in archivedatabase 208, such that any instances of activation or deactivation ofinsurance coverage recorded while device 300 is in offline mode can beaudited as necessary in an insurance claim made by customer 201.

FIG. 6 shows a flowchart of an illustrative method 600 for verifyingactivation of insurance coverage upon receiving an insurance claim madeby a customer 201, in accordance with embodiments of the presentinvention. As shown, at block 602, a customer may submit an insuranceclaim. At decision block 604, method 600 may check whether the claimdata is complete. If no, method 600 may require customer 201 to resubmita claim. If yes, method 600 may proceed to block 606, where the claimdata is entered into the system (e.g. system 200 of FIG. 2).

Method 600 may then proceed to decision block 608, where method 600determines whether the insurance claim is for an insurance “on demand”product. If no, method 600 may proceed to a standard “business as usual”claim process. If yes, method 600 may proceed to block 610.

At block 610, in order to determine whether the customer's insuranceclaim is valid, method 600 may determine whether insurance was active atthe time of the accident by correlating the accident time with theactivation status as recorded in an archive database (e.g. archivedatabase 208 of FIG. 2) or a status change database (e.g. status changedatabase 210 of FIG. 2). There may be a number of ways to verify this,depending on the selected configuration. For example, if activation ofinsurance coverage by customer 201 automatically starts a predeterminedtime period for coverage (e.g. 24 hours), then it will be necessary onlyto confirm that the accident took place within that 24 hour period fromactivation. This may be verified, for example, by determining the timeof the accident as reported by the customer 201, which may becorroborated with the time of the accident as reported by a lawenforcement authority, or by another party involved in an accident.Alternatively, in order to verify that insurance was active at the timeof coverage, customer 201 may be required to report the accidentimmediately via any access methods or devices that may be available. Ifcustomer 201 happens to be using device 300 in offline mode when anaccident occurs, customer 201 may, for example, either enter a requestto submit a claim for insurance, or simply turn off the device 300.Device 300 may be configured to record the date/time to non-volatilestorage means 324 upon being turned off. When device 300 is reset, itmay be configured to default to a read only mode where no furtherchanges may be made. Should customer 201 be unable to report theaccident immediately for whatever reason, the default option may beverification of the time of the accident through a law enforcementauthority, or corroboration by a third party.

Whichever way is used, if insurance activation at the time of theaccident is verified, method 600 may proceed to block 622 and processthe claim with confirmation of insurance coverage. Otherwise, if it isdetermined that insurance coverage was not activated at the time of theaccident, method 600 may proceed to block 624 where the insurance claimis denied.

While illustrative embodiments of the invention have been describedabove, it will be appreciated by those skilled in the art thatvariations and modifications may be made. For example, device 300 may beprovided in various alternative configurations, with various ways foractivating or deactivating insurance. However, in each case, a requestfor activation or deactivation will be recorded in a non-volatilestorage that is tamper-proof or tamper-evident, either in an offlinemode (e.g. within device 300) or within system 200 as described by wayof example above.

What is claimed is:
 1. A computer program product, comprising a computerreadable storage media having computer readable program code storedtherein, said computer readable program code configured to be executedby a processor comprised by a insurance data processing system (IDPS) toimplement a method for processing insurance coverage requests, said IDPSfurther comprising: (a) a wireless device consisting of a mobileelectronic device provided to a customer, (b) an insurance activationserver, and (c) an archive database connected to the insuranceactivation server, said method comprising: receiving, by the IDPS, aplurality of requests from the customer relating to insurance coveragefor the customer, each request requesting activation or deactivation ofthe insurance coverage; confirming by the IDPS, for each requestreceived, that it is permissible for the IDPS to accommodate eachrequest based on each request's requested activation or deactivation;and after said confirming for each request, archiving by the IDPS eachrequest in a non-volatile storage medium of the IDPS; wherein the mobileelectronic device comprises the non-volatile storage medium; whereinsaid receiving, said confirming, and said archiving are performed withrespect to each request by the mobile electronic device while the mobileelectronic device is in an offline mode, said offline mode characterizedby the mobile electronic device being disconnected from the insuranceactivation server and any other external communication device; whereinafter said archiving is performed, the method further comprises: while aconnection is established between the mobile electronic device and theinsurance activation server, said server updating the archive databasewith each request archived in the non-volatile storage medium; whereinthe method further comprises determining that an insurance claim by thecustomer relating to an accident is valid by verifying that theinsurance coverage was active at a time when the accident occurred basedon the most recent requested activation or deactivation, said verifyingoccurring when the mobile electronic device is connected to theinsurance activation server and comprising determining by the serverthat a request to submit the insurance claim is stored in the mobileelectronic device operating in the offline mode.
 2. The computer programproduct of claim 1, wherein the method further comprises: said mobileelectronic device tracking insurance coverage credits in a bank whilethe mobile electronic is operating in the offline mode, said insurancecoverage credits being credits for insurance coverage time purchased bythe customer.
 3. The computer program product of claim 2, wherein theinsurance coverage credits are time credits in a bank tracked by themobile device.
 4. The computer program product of claim 3, wherein themethod further comprises: in response to a new request received from thecustomer for activation of the insurance coverage for a time duration,ascertaining that the remaining amount of time of said time creditexceeds the time duration; and responsive to said ascertaining, grantingthe new request.
 5. The computer program product of claim 1, wherein therequests of the plurality of requests are ordered in a time sequence. 6.The computer program product of claim 1, wherein the mobile electronicdevice is configured to be used in the offline mode by the customer toactivate the insurance coverage from any insurer of a plurality ofinsurers offering competing insurance products pertaining to theinsurance coverage.
 7. The computer program product of claim 1, whereineach request requesting activation or deactivation is implementedthrough use of a single push button in the mobile electronic device totoggle between said activation and said deactivation.
 8. The computerprogram product of claim 1, wherein said verifying further comprisesthat a date/time stored in the mobile electronic device in response tothe mobile electronic device having been turned off and entered into aread-only mode corresponds to the time when the accident occurred.
 9. Aninsurance data processing system (IDPS) comprising a processor and acomputer readable memory unit coupled to the processor, said memory unitcontaining program code configured to be executed by the processor toimplement a method for processing insurance coverage requests, said IDPSfurther comprising: (a) a wireless device consisting of a mobileelectronic device provided to a customer, (b) an insurance activationserver, and (c) an archive database connected to the insuranceactivation server, said method comprising: receiving, by the IDPS, aplurality of requests from the customer relating to insurance coveragefor the customer, each request requesting activation or deactivation ofthe insurance coverage; confirming by the IDPS, for each requestreceived, that it is permissible for the IDPS to accommodate eachrequest based on each request's requested activation or deactivation;and after said confirming for each request, archiving by the IDPS eachrequest in a non-volatile storage medium of the IDPS; wherein the mobileelectronic device comprises the non-volatile storage medium; whereinsaid receiving, said confirming, and said archiving are performed withrespect to each request by the mobile electronic device while the mobileelectronic device is in an offline mode, said offline mode characterizedby the mobile electronic device being disconnected from the insuranceactivation server and any other external communication device; whereinafter said archiving is performed, the method further comprises: while aconnection is established between the mobile electronic device and theinsurance activation server, said server updating the archive databasewith each request archived in the non-volatile storage medium; whereinthe method further comprises determining that an insurance claim by thecustomer relating to an accident is valid by verifying that theinsurance coverage was active at a time when the accident occurred basedon the most recent requested activation or deactivation, said verifyingoccurring when the mobile electronic device is connected to theinsurance activation server and comprising determining by the serverthat a request to submit the insurance claim is stored in the mobileelectronic device operating in the offline mode.
 10. The data processingsystem of claim 9, wherein the insurance coverage credits are timecredits in a bank tracked by the mobile device.
 11. The data processingsystem of claim 10, wherein the method further comprises: in response toa new request received from the customer for activation of the insurancecoverage for a time duration, ascertaining that the remaining amount oftime of said time credit exceeds the time duration; and responsive tosaid ascertaining, granting the new request.
 12. The data processingsystem of claim 9, wherein the requests of the plurality of requests areordered in a time sequence.
 13. The data processing system of claim 9,wherein the mobile electronic device is configured to be used in theoffline mode by the customer to activate the insurance coverage from anyinsurer of a plurality of insurers offering competing insurance productspertaining to the insurance coverage.
 14. The data processing system ofclaim 9, wherein each request requesting activation or deactivation isimplemented through use of a single push button in the mobile electronicdevice to toggle between said activation and said deactivation.
 15. Thedata processing system of claim 9, wherein said verifying furthercomprises that a date/time stored in the mobile electronic device inresponse to the mobile electronic device having been turned off andentered into a read-only mode corresponds to the time when the accidentoccurred.
 16. The data processing system of claim 9, wherein the methodfurther comprises: said mobile electronic device tracking insurancecoverage credits in a bank while the mobile electronic is operating inthe offline mode, said insurance coverage credits being credits forinsurance coverage time purchased by the customer.